Open mergeback PR last #3287
Merged
Open mergeback PR last #3287
+10
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reduces the likelihood of publishing a tag but not a release.
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR reorders workflow steps to create the mergeback PR after the GitHub release is created, reducing the likelihood of publishing a tag but not a release.
- The "Create mergeback branch and PR" step is moved from before the release creation to after it
- The step execution order now ensures the release is fully published before initiating the mergeback process
henrymercer
commented
Nov 13, 2025
| --notes-file "$PARTIAL_CHANGELOG" | ||
| - name: Create mergeback branch and PR | ||
| if: ${{ endsWith(github.ref_name, steps.getVersion.outputs.latest_release_branch) }} |
Contributor
Author
There was a problem hiding this comment.
I also changed this so that we will try to open the mergeback even if the tag exists. This means we can retry generating the mergeback if this workflow fails, even if the tag is already published.
esbena
approved these changes
Jan 6, 2026
This was referenced Jan 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reduces the likelihood of publishing a tag but not a release.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Dev only
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Merge / deployment checklist